IDMS regions (central versions) STC and or batch jobs are not defined in accordance with the proper security requirements.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-47	ZIDM0030	SV-7310r2_rule	DCCS-1 DCCS-2	Medium

Description
Improperly defined IDMS central versions (CVs) have the potential to bypass security controls and obtain unauthorized access to system resources. This could potentially compromise the confidentiality, integrity, and availability of the operating system, ACP, and customer data.

STIG	Date
z/OS RACF STIG	2015-03-27

Details

Check Text ( C-20582r1_chk )
a) Refer to the following reports produced by the RACF Data Collection: - RACFCMDS.RPT(LISTUSER) - DSMON.RPT(RACSPT) Refer to the IDMS Worksheet in the z/OS STIG Adendum and copy it and fill out the information for each IDMS CV running on this LPAR. b) Ensure the following items are in effect: - A unique userid is associated with each IDMS CV. - Userids of IDMS CVs that runs as a started task, has a matching profile defined to the STARTED resource class. c) If the items in (b) are true, there is NO FINDING. d) If the items in (b) is untrue, this is a FINDING.

Check Text ( C-20582r1_chk )

a) Refer to the following reports produced by the RACF Data Collection:

- RACFCMDS.RPT(LISTUSER)
- DSMON.RPT(RACSPT)

Refer to the IDMS Worksheet in the z/OS STIG Adendum and copy it and fill out the information for each IDMS CV running on this LPAR.

b) Ensure the following items are in effect:

- A unique userid is associated with each IDMS CV.

- Userids of IDMS CVs that runs as a started task, has a matching profile defined to the STARTED resource class.

c) If the items in (b) are true, there is NO FINDING.

d) If the items in (b) is untrue, this is a FINDING.

Fix Text (F-18530r1_fix)
IDMS can be run as either a batch job or an STC. In either case, a unique userid must be associated with each IDMS region or CV. The userid must be defined with the RACF PROTECTED attribute. No default userids will be used. Each CV’s userid will only have access to those resources required by IDMS to perform its function. Ensure the following items are in effect: - A unique userid is associated with each IDMS CV. - The userid is defined with the RACF PROTECTED attribute. - Userids of IDMS CVs that runs as a started task, has a matching profile defined to the STARTED resource class. Command Samples: 1. To add (define) a user to RACF with the PROTECTED attribute: ADDUSER CV100 NAME('STC, IDMS CV100') DFLTGRP(STC) OWNER(STC) NOPASS 2. To define a STARTED class profile to assign a userid of CV100 with a started proc named CV100: RDEF STARTED CV100.** UACC(NONE) OWNER(ADMIN) STDATA(USER(CV100) GROUP(STC) TRACE(YES)) 2.

Fix Text (F-18530r1_fix)

IDMS can be run as either a batch job or an STC. In either case, a unique userid must be associated with each IDMS region or CV. The userid must be defined with the RACF PROTECTED attribute. No default userids will be used. Each CV’s userid will only have access to those resources required by IDMS to perform its function.

Ensure the following items are in effect:

- A unique userid is associated with each IDMS CV.

- The userid is defined with the RACF PROTECTED attribute.

- Userids of IDMS CVs that runs as a started task, has a matching profile defined to the STARTED resource class.

Command Samples:

1. To add (define) a user to RACF with the PROTECTED attribute:

ADDUSER CV100 NAME('STC, IDMS CV100') DFLTGRP(STC) OWNER(STC) NOPASS

2. To define a STARTED class profile to assign a userid of CV100 with a started proc named CV100:

RDEF STARTED CV100.** UACC(NONE) OWNER(ADMIN) STDATA(USER(CV100) GROUP(STC) TRACE(YES))

2.